home *** CD-ROM | disk | FTP | other *** search
- Path: nwlink.com!usenet
- From: grtorlba@nwlink.com (George R. Torralba)
- Newsgroups: comp.std.c,comp.lang.c,comp.lang.basic.visual.misc
- Subject: Re: DLLs
- Date: Mon, 04 Mar 1996 12:09:10 GMT
- Organization: None whatsoever
- Message-ID: <313adc9f.17275053@news.nwlink.com>
- References: <NEWTNews.825739945.5620.david@baldar.abs.net> <3138938a.225633183@news.intr.net>
- NNTP-Posting-Host: port27.annex2.nwlink.com
- X-Newsreader: Forte Agent .99d/32.182
-
-
- I don't see why anyone should forget about DLLs and opt for OCXs based
- on your argument. Yeah it can fire events. So what? Did you mention
- the overhead? If the guy's just exporting functions why build an OCX?
-
- George
-
- In article , rodhew@intr.net (Rod Hewitt) wrote:
-
- >david@baldar.abs.net wrote:
- >
- >>
- >>Are there any good references out there on writing DLLs? I just got MS C++
- >>4.0. Writing the .c is easy. But the .def and .mak still eludes me (the
- >>online notes with MS C++ leave something to be desired). Any recommendations?
- >> Thanks.
- >
- >If your targetting the DLL at VB, I'd recommend you forget about DLLs
- >and write OCXes instead. The App Wizard and Class Wizard make it very
- >easy to write C++ code that interfaces to VB. Plus with OCXes you can
- >easily fire events in VB and not have to worry about a ton of Define
- >Function statements.
- >
- >Regards,
- >Rod
- >
-
-
- ===============================================================================
- George R. Torralba xxxxxxxxxxxx Batang Cebu!!!
- Seattle, Washington 206.227.0821 MIME mail accepted
- ===============================================================================
-